System and method for adaptive contextual communications

ABSTRACT

A system and method for adaptive contextual communications is disclosed. A system that incorporates teachings of the present disclosure may include, for example, a call gateway having a controller element that retrieves a communication context from a call setup request directed to a called party&#39;s Terminal Device (TD) by a calling party&#39;s TD, and informs a first mapping generator of said communication context to determine a content mapping scheme for content exchanged between the calling party&#39;s and called party&#39;s TDs. Additional embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 60/868,063, filed Nov. 30, 2006, the entire contents ofwhich are incorporated by reference herein.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to communication systems, andmore specifically to a system and method for adaptive contextualcommunications.

BACKGROUND

A trend towards convergence between computing and communicationtechnologies has given consumers to select from a number of devices toperform voice, video and/or data communications (e.g., cell phones,laptop and desktop computers, Personal Digital Assistants (PDAs),Television sets, Text messaging devices, and so on). Typically aconsumer's selective use of these devices is based on need,availability, and convenience. When a consumer desires to transitionfrom a device actively engaged in a communication session to anotherdevice (e.g., cell phone to cordless phone), said consumer mustterminate the communication session and re-engage it with the newdevice. This process can be slow, cumbersome and undesirable.

A need therefore arises for a system and method for adaptive contextualcommunications.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying figures, where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, together with the detailed description below, are incorporated inand form part of the specification, and serve to further illustrate theembodiments and explain various principles and advantages, in accordancewith the present disclosure.

FIG. 1 depicts an exemplary block diagram of a communication system;

FIG. 2 depicts an exemplary flowchart of a method operating in thecommunication system; and

FIG. 3 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methodologiesdiscussed herein.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions of some of the elements inthe figures may be exaggerated relative to other elements to help toimprove understanding of embodiments of the present disclosure.

DETAILED DESCRIPTION

The specification and figures are to be regarded in an illustrativerather than a restrictive sense, and all such modifications are intendedto be included within the scope of present invention. The benefits,advantages, solutions to problems, and any element(s) that may cause anybenefit, advantage, or solution to occur or become more pronounced arenot to be construed as a critical, required, or essential features orelements of any or all the claims. The invention is defined solely bythe appended claims including any amendments made during the pendency ofthis application and all equivalents of those claims as issued.

Embodiments in accordance with the present disclosure provide a systemand method for adaptive contextual communications.

In a first embodiment of the present disclosure, a call gateway can havea controller element that retrieves a communication context from a callsetup request directed to a called party's Terminal Device (TD) by acalling party's TD, and informs a first mapping generator of saidcommunication context to determine a content mapping scheme for contentexchanged between the calling party's and called party's TDs.

In a second embodiment of the present disclosure, a mapping generatorcan have a controller element that determines a content mapping schemefor content exchanged between a calling party's and called party's TDsaccording to a communication context associated with a call setuprequest initiated by the calling party's TD and one or more operatingparameters of the called party's TD.

In a third embodiment of the present disclosure, a media gateway canhave a controller element that adapts content exchanged between a calledparty's and calling party's TDs according to a content mapping schemesupplied by a mapping generator.

In a fourth embodiment of the present disclosure, a device can have acontroller element that generates a Call Detail Record (CDR) comprisinginformation associated with an exchange between first and second mappinggenerators that determine a content mapping scheme between first andsecond TDs.

FIG. 1 depicts an exemplary communication system 100. The communicationsystem 100 can comprise one or more operators that manage a network 101having one or more Call Gateways (CGs) 102, Mapping Generators (MGs)104, media gateways 106, and Call Detail Record (CDR) database systems108. The CGs 102 can represent a switch for wired and/or wirelesscommunications that can route calls, handoff calls, and/or interact withMGs 104 to establish a content mapping scheme for a communicationsession between terminal devices (TDs) 110. The MGs 104 can be utilizedto negotiate with other MGs the content mapping scheme which is in turnused by the media gateways 106 to adapt the exchange of content betweenTDs 110 of disparate capabilities. The CDR database systems 108 can beutilized to record CDRs associated with the call session. TDs 110 canrepresent any computing device capable of wired and/or wirelesscommunications (e.g., cell phone, cordless phone, PDA, desktop or laptopcomputer, set-top-box or STB, residential gateway, and so on).

The network elements of the communication system 100 (i.e., the CG, MG,media device, CDR database system, and TDs) utilize common technologiessuch as a controller coupled to support technologies (e.g., display,keyboard/pad, etc.) and associated communication technologies to performthe functions described in the present disclosure. Additionally, thecommunication system 100 can be architected to support circuit and/orpacket switched technologies. For example, portions of the communicationsystem can operate as a Public Switched Telephone Network (PSTN)utilizing SS7 as its signaling system. Other portions of thecommunication system can be architected according to an IP MultimediaSubsystem (IMS) architecture utilizing a Session Initiation Protocol(SIP) or derivatives thereof to support multiple embodiments of IPcommunications (e.g., Voice over IP, video, and data). Any number ofwireless communication protocols can be supported by a portion of thenetwork elements of said system 100 (e.g., CDMA, GSM, UMTS, EVDO, etc.).

FIG. 2 depicts a method 200 operating in the communication system 100.Method 200 can be utilized for establishing communication between TDs110 having disparate functionalities as well as for transitioningcommunications from one TD to another while actively engaged in acommunication session, and/or for adapting to a handoff from one networkto another when one of the TDs roams to a new network. With theseprinciples in mind, method 200 begins with step 201 where the MGs 104can be programmed to monitor and/or receive registrations and/ornotifications from the TDs 110. The registrations or notifications caninclude without limitation changes in operating parameters of the TDs110, current user activity at the TDs, or one or more user preferencesfor utilizing TDs within or across networks. The aforementionedregistrations and/or notifications can be utilized by the MGs 104 todetermine a suitable content mapping scheme between TDs 110 as will bediscussed shortly.

It should be noted that the dashed arrow between steps 201 and 202 is anindication that step 201 can occur anywhere and at anytime in theflowchart illustration of method 200. Thus the position of step 201 inthe flowchart of FIG. 2 is illustrative. In this context, step 201 canbe prompted in real-time by the TDs 110 and/or can be polledperiodically by the MGs 104 as a background process.

In step 202 a CG 102 can receive a call setup request directed to acalled party's TD 110 by a calling party's TD. In step 204, the CG 102retrieves a communication context from the call setup request. Retrievalof the communication context can be from a signaling portion of the callsetup request (e.g., SS7, SIP, H.323, etc.). The communication contextidentifies a type of communication session requested (voice, video,and/or data). The communication context can also identify a type ofservice requested (e.g., Voice over IP or VoIP, IP video, PSTN voice,streaming service, etc.). Accordingly, the communication context can beas explicit as needed to determine the service resources necessary toestablish communications for the calling party's TD 110.

To assure a compatible communications between the calling and calledparties' TDs 110, the CG 102 proceeds to step 206 where it submits thecommunication context to an MG 104 associate with the calling party'sTD. The MG 104 proceeds to step 208 where it contacts an MG associatedwith the called party's TD 110 to determine one or more operatingparameters of the called party's TD. The information retrieved from thecalled party's MG 104 can be stored in its memory based on a priorauthorization and authentication cycle when the called party's TD 110roamed into the network 101 or after a power-up cycle of the TD on saidnetwork. Alternatively, the MG 104 associated with the called party's TD110 can request this information from the called party's TD in responseto a request from another MG.

The operating parameters associated with the called party's TD 110 caninclude without limitation one or more device capabilities of the calledparty's TD (e.g., video, high-speed data, etc.), one or more operatingpreferences of the called party's TD (e.g., video for some callers andnot others, instant messaging or IM preference over SMS messages, buddylist preferences, etc.), and/or one or more activities taking place atthe called party's TD (e.g., active IM session, active conference call,etc.). Other suitable parameters that can prove useful for enablingcommunications between the called and calling party's TDs 110 can beapplied to the present disclosure.

Once the operating parameters of the called party's TD 110 are known,the MG 104 of the calling party's TD 110 can determine a content mappingscheme in step 210 according to said parameters and the communicationcontext given in step 206. The content mapping scheme can consist of atranscoding scheme that maps a video call to a voice-only call in theevent that the called TD is limited to voice-only communications or hasa preference for voice-only communications for certain calling parties.Other conceivable content mapping schemes can be applied to the presentdisclosure (e.g., voice to IM, VoIP to PSTN voice, full bandwidth videoto streaming video, etc.). In step 212, the MG 104 informs a mediagateway 106 associated with the calling party's TD 110 of the contentmapping scheme. In this same step, the MG 104 instructs the CG 102 thatreceived the call setup request in step 202 to establish a communicationsession between the calling and called parties' TDs 110. At this point,the media gateway 106 of the called party's TD 110 transcodes contentexchanged between said TDs according the content mapping scheme andcommunication ensues.

In step 214, CDR database system 108 records the transactions takingplace between the CG 102, MG 104, and media gateway 106. The dashedarrows flowing from step 212 to step 214 and from step 214 to step 216indicate that the recordation of the foregoing activities in step 214can take place anywhere and at anytime in the flowchart of method 200.Thus the position of step 214 in the flowchart of FIG. 2 isillustrative. In this context, step 214 can be prompted in real-time bythe CG 102, MG 104, or media gateway 106 and/or can be polledperiodically by the CDR database system 108 as a background process.

The information recorded can include without limitation informationassociated with the call setup request (e.g., calling number, TelephoneNumber Mapping or ENUM ID, etc.), a media type used for contentexchanged between the TDs 110, a service used to deliver the media type,a duration of communication between the TDs, a type of media transcodingused by the media gateway 106, and/or information exchanged between theMGs 104 associated with the called and calling parties' TDs. The CDR canfurther include event information associated with the CG 102establishing a communication session between TDs 110, a hand off managedby the CG taking place between TDs or networks, the negotiation ofoperating parameters of the TDs between MGs 104, the generation of thecontent mapping scheme used between the TDs, and/or the adaptation ofcontent by a media gateway 106 between the TDs according to the contentmapping scheme.

Either of the CGs 102 associated with the called or calling parties' TDs102 can be further programmed in step 216 to monitor a request totransition to a new TD 110. The request can come from the new TD 110 inthe form of a message indicating a desire to transition thecommunication session to the new TD 110. This request can be entered bythe end user of said new TD 110 by way of its User Interface (UI). If arequest is detected by the CG 102 in step 216, it proceeds to step 218where it submits to an MG 104 associated with the new TD 110 a newcommunication context retrieved from a corresponding call setup requestgenerated by the new TD. In step 220, said MG 104 contacts the MG of theremaining TD (i.e., the TD currently engaged in the communicationsession) to determine its operating parameters. In step 222, the MG 104determines a new content mapping scheme according to the operatingparameters of the remaining TD and the new communication context. Thenew content mapping scheme is communicated in step 224 to the mediagateway 106 associated with the new TD 110. In step 224 the MG 104further instructs the CG 102 that detected the TD 110 switch request totransition the communication session to the new TD and the remaining TD.From this point communication ensues between the new and remaining TDs110 according to the content mapping scheme managed by the respectivemedia gateways 106 of said TDs.

The CGs 102 thereafter proceed to step 226 to determine if a handoffbetween networks 101 is requested by a roaming TD 110. Alternatively,step 226 can be entered if no transition between TDs is detected by theCGs 102 in step 216. If no handoff is detected, the CGs 102 proceed backto step 216 where they again monitor for a request to switch to a new TD110. The CGs 102 continue to check between handoffs and TD 110 switchingevents until the communication session is terminated between theactively engaged TDs.

If a handoff is detected by one of the CGs 102, the detecting CGproceeds to step 228 where it informs the CG of the remaining TD 110 ofthe imminent handoff to the new network. In step 230, the CG 102 of theremaining TD 110 instructs its MG 104 to determine a new content mappingscheme by contacting the MG of the new network to determine itscapabilities. From this information, the MG 104 of the remaining TD'snetwork formulates a new content mapping scheme which is submitted toits media gateway 106. At this point, the media gateway 106 of theremaining TD 110 adapts to the new capabilities of the new network 101.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope andspirit of the claims described below. For example, message exchangesbetween the CGs 102, MGs 104, and media gateways 106 can be rearrangedin ways other than those presented here to accomplish the same orsimilar content mapping schemes. Additionally, events that trigger thesteps presented by method 200 can differ without affecting the abilityto nearly seamlessly support communication transitions betweenfunctionally disparate TDs while said TDs roam between operator networksor an end user transitions to another TD. These are but a few examplesof modifications that can be applied to the present disclosure withoutdeparting from the scope of the claims stated below. Accordingly, thereader is directed to the claims section for a fuller understanding ofthe breadth and scope of the present disclosure.

FIG. 3 is a diagrammatic representation of a machine in the form of acomputer system 300 within which a set of instructions, when executed,may cause the machine to perform any one or more of the methodologiesdiscussed above. In some embodiments, the machine operates as astandalone device. In some embodiments, the machine may be connected(e.g., using a network) to other machines. In a networked deployment,the machine may operate in the capacity of a server or a client usermachine in server-client user network environment, or as a peer machinein a peer-to-peer (or distributed) network environment. The machine maycomprise a server computer, a client user computer, a personal computer(PC), a tablet PC, a laptop computer, a desktop computer, a controlsystem, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. It will be understood that a deviceof the present disclosure includes broadly any electronic device thatprovides voice, video or data communication. Further, while a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The computer system 300 may include a processor 302 (e.g., a centralprocessing unit (CPU), a graphics processing unit (GPU, or both), a mainmemory 304 and a static memory 306, which communicate with each othervia a bus 308. The computer system 300 may further include a videodisplay unit 310 (e.g., a liquid crystal display (LCD), a flat panel, asolid state display, or a cathode ray tube (CRT)). The computer system300 may include an input device 312 (e.g., a keyboard), a cursor controldevice 314 (e.g., a mouse), a disk drive unit 316, a signal generationdevice 318 (e.g., a speaker or remote control) and a network interfacedevice 320.

The disk drive unit 316 may include a machine-readable medium 322 onwhich is stored one or more sets of instructions (e.g., software 324)embodying any one or more of the methodologies or functions describedherein, including those methods illustrated above. The instructions 324may also reside, completely or at least partially, within the mainmemory 304, the static memory 306, and/or within the processor 302during execution thereof by the computer system 300. The main memory 304and the processor 302 also may constitute machine-readable media.Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Applications that may include the apparatusand systems of various embodiments broadly include a variety ofelectronic and computer systems. Some embodiments implement functions intwo or more specific interconnected hardware modules or devices withrelated control and data signals communicated between and through themodules, or as portions of an application-specific integrated circuit.Thus, the example system is applicable to software, firmware, andhardware implementations.

In accordance with various embodiments of the present disclosure, themethods described herein are intended for operation as software programsrunning on a computer processor. Furthermore, software implementationscan include, but not limited to, distributed processing orcomponent/object distributed processing, parallel yprocessing, orvirtual machine processing can also be constructed to implement themethods described herein.

The present disclosure contemplates a machine readable medium containinginstructions 324, or that which receives and executes instructions 324from a propagated signal so that a device connected to a networkenvironment 326 can send or receive voice, video or data, and tocommunicate over the network 326 using the instructions 324. Theinstructions 324 may further be transmitted or received over a network326 via the network interface device 320.

While the machine-readable medium 322 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present disclosure.

The term “machine-readable medium” shall accordingly be taken toinclude, but not be limited to: solid-state memories such as a memorycard or other package that houses one or more read-only (non-volatile)memories, random access memories, or other re-writable (volatile)memories; magneto-optical or optical medium such as a disk or tape; andcarrier wave signals such as a signal embodying computer instructions ina transmission medium; and/or a digital file attachment to e-mail orother self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. Accordingly, the disclosure is considered to include any one ormore of a machine-readable medium or a distribution medium, as listedherein and including art-recognized equivalents and successor media, inwhich the software implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are periodicallysuperseded by faster or more efficient equivalents having essentiallythe same functions. Accordingly, replacement standards and protocolshaving the same functions are considered equivalents.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Otherembodiments may be utilized and derived therefrom, such that structuraland logical substitutions and changes may be made without departing fromthe scope of this disclosure. Figures are also merely representationaland may not be drawn to scale. Certain proportions thereof may beexaggerated, while others may be minimized. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separately claimed subject matter.

1. A Call Gateway (CG), comprising a controller element that retrieves a communication context from a call setup request directed to a called party's Terminal Device (TD) by a calling party's TD, and informs a first mapping generator of said communication context to determine a content mapping scheme for content exchanged between the calling party's and called party's TDs.
 2. The CG of claim 1, wherein the first mapping generator: contacts a second mapping generator to determine one or more operating parameters of the called party's TD, and determines the content mapping scheme according to the one or more operating parameters of the called party's TD and the communication context requested by the calling party's TD.
 3. The CG of claim 2, wherein the first mapping generator: informs a media gateway of the content mapping scheme for adapting content exchanged between the called party's and calling party's TDs, and instructs the controller element to establish a communication session between said called party's and calling party's TDs.
 4. The CG of claim 3, wherein the communication context comprises at least one among routing a call between the calling party's and called party's TDs with one or more media streams or services established therebetween, handing off between networks a portion of a communication session established between the calling party's and called party's TDs, and monitoring the one or more media streams and services in the call, and wherein a Call Detail Record (CDR) is generated from information supplied by the controller element, the first mapping generator and the media gateway, and wherein the CDR comprises at least one among information associated with the call setup request, a media type used for content exchanged between the TDs, a service used to deliver the media type, a duration of communication between the TDs, a type of media transcoding used by the media gateway, and information exchanged between the first and second mapping generators.
 5. The CG of claim 3, wherein at least a portion of the CG, the first and second mapping generators, and the media gateway conforms to an Internet Protocol Multimedia Subsystem (IMS) architecture, and wherein at least a portion of signaling information exchanged between the CG, the first and second mapping generators, and the media gateway conforms to a Session Initiation Protocol (SIP).
 6. The CG of claim 3, wherein the controller element: detects a desire by the calling party or the called party to transition to a new TD, and instructs a mapping generator associated with the new TD to determine a new mapping scheme for content exchanged between the new TD and the remaining TD.
 7. The CG of claim 6, wherein the controller element: receives a new call setup request from the new TD, retrieves a new communication context from the new call setup request, and informs the mapping generator associated with the new TD of the new communication context
 8. The CG of claim 7, wherein the mapping generator associated with the new TD: contacts the remaining mapping generator to determine one or more operating parameters of the remaining TD, and determines a new content mapping scheme according to the one or more operating parameters of the remaining TD and the new communication context.
 9. The CG of claim 8, wherein the mapping generator associated with the new TD: informs a media gateway associated therewith of the new mapping scheme for adapting content exchanged between the new TD and the remaining TD, and instructs the controller element to transition the communication session to the new TD and the remaining TD.
 10. The CG of claim 3, wherein a select one of the CGs of the calling and called TDs detects a need to handoff a portion of the communication session to a new network in response to one of said TDs roaming into said new network, wherein said detecting CG instructs the CG of the remaining TD of the handoff to the new network, wherein the CG of the remaining TD instructs its mapping generator to determine a new content mapping scheme according to an exchange with a mapping generator of the new network, and wherein the mapping generator of the remaining TD informs its media gateway of the new mapping scheme.
 11. A mapping generator, comprising a controller element that determines a content mapping scheme for content exchanged between a calling party's and called party's Terminal Devices (TDs) according to a communication context associated with a call setup request initiated by the calling party's TD and one or more operating parameters of the called party's TD.
 12. The mapping generator of claim 11, wherein the controller element: contacts a second mapping generator to determine one or more operating parameters of the called party's TD, and receives the communication context from a Call Gateway (CG) that retrieves said communication context from the call setup request.
 13. The mapping generator of claim 12, wherein the one or more operating parameters comprise at least one among one or more device capabilities of the called party's TD, one or more preferences of the called party, and one or more user activities taking place at the called party's TD.
 14. The mapping generator of claim 12, wherein the controller element: informs a media gateway of the content mapping scheme for adapting content exchanged between the called party's and calling party's TDs, and instructs the CG to establish a communication session between said called party's and calling party's TDs.
 15. The mapping generator of claim 14, wherein at least a portion of the CG, the first and second mapping generators, and the media gateway conforms to an Internet Protocol Multimedia Subsystem (IMS) architecture, wherein at least a portion of signaling information exchanged between the CG, the first and second mapping generators, and the media gateway conforms to a Session Initiation Protocol (SIP), and wherein a Call Detail Record (CDR) is generated from information supplied by the CG, the mapping generator and the media gateway.
 16. The mapping generator of claim 11, wherein the controller element receives a registration or notification of at least one among changes in operating parameters of the calling party's or called party's TD, current user activity at the calling party's or called party's TD, and one or more preferences of the called or calling party within or across networks.
 17. A media gateway, comprising a controller element that adapts content exchanged between a called party's and calling party's Terminal Devices (TDs) according to a content mapping scheme supplied by a mapping generator.
 18. The media gateway of claim 17, wherein the mapping generator determines the content mapping scheme from a communication context associated with a call setup request initiated by the calling party's TD and one or more operating parameters of the called party's TD.
 19. The media gateway of claim 17, wherein a Call Gateway (CG) supplies the communication context to the mapping generator.
 20. The media gateway of claim 18, wherein the CG retrieves the communication context from a call setup request initiated by the calling party's TD.
 21. The media gateway of claim 19, wherein at least a portion of the CG, the mapping generator, and the media gateway conforms to an Internet Protocol Multimedia Subsystem (IMS) architecture, and wherein at least a portion of signaling information exchanged between the CG, the first and second mapping generators, and the media gateway conforms to a Session Initiation Protocol (SIP), and wherein a Call Detail Record (CDR) is generated from information supplied by the CG, the mapping generator and the media gateway.
 22. A device, comprising a controller element that generates a Call Detail Record (CDR) comprising information associated with an exchange between first and second Mapping Generators (MGs) that determine a content mapping scheme between first and second terminal devices (TDs).
 23. The device of claim 22, wherein generation of the CDR is associated with at least one among one or more events comprising: a Call Gateway (CG) establishing a communication session between the first and second TDs, the CG handing off a portion of the communication session, negotiation of operating parameters of the first and second TDs between the first and second MGs, generation of the content mapping scheme, and a media gateway adapting content exchanged between the first and second TDs according to the content mapping scheme.
 24. The device of claim 22, wherein the CDR further comprises at least one among information associated with a call setup request between the TDs, a media type used for content exchanged between the TDs, a service used to deliver the media type, a duration of communication between the TDs, and a type of media transcoding used by a media gateway to establish communication between the TDs. 